COMMENT ⊗   VALID 00002 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	∂27-AUG-73  1216		LSP,TVR
C00007 ENDMK
C⊗;
∂27-AUG-73  1216		LSP,TVR
 The reasom that typeahead is flushed when ILISP is started is that }
 ERRSET flushs TTY buffer irrespective of second arg.  That should be
 fixed in ILISP.MAC.
 			Tovar
 
∂27-AUG-73  0947		2,TVR
 (PRIN1(QUOTE /)/"))	results in	 /)/"
 (PRIN1(QUOTE /"/)))	results in	 ")

 This clearly loses.
 			Tovar

 
∂17-JUN-73  1433		FOO,DBA
 Don't know when you will get this - more details on the BREAK problem.
 It seems to be connected with interrupting (GO foo) statements. In this
 case the OK or GO does not reset the break depth counter,and the break
 is not properly released.  The next interrupt of GO gives a depth of
 one more, but doing ↑ causes one of two kinds of lossage:
 1.  xxxxxxx ILL MEM REF FROM UNBREAK0
     (/BREAK1 BROKEN)
 in which case the only escape is ↑↑ (which continues to work)
 2.  xxxxxxx ILL MEM REF FROM SETARG
     NON-NUMERIC ARGUMENT
 at which time the thing goes into a tight loop from which ther
 is no escape.
 If you don't tell me you have got this message soon, I'll try
 Daryle Lewis at BBN.
 In case anyone else reads this, the problem is as follows: funnies
 when interrupting
 (PROG NIL LBL (PRINC @FOO)(GO LBL))
 If the (GO LBL) is interrupted then on doing OK or GO and another
 interrupt, the second break thinks it is at a depth of 2. Now read
 top of message down!

∂19-JUN-73  1400		network site BBN
 -------
 Date: 19-JUN-73 1701-EDT
 From: LEWIS at BBN-TENEX
 Re:   GO
 - - - -
 BRUCE,
 THE PROBLEM WITH GO (AND RETURN FOR THAT MATTER) IS THAT
 IT UNWINDS THE STACK BACK TO THE LAST PROG. HOWEVER, IT DOES NOT
 UNWIND ERRSETS. SINCE THE GO OR OK EVALUATES ITS EXPRESSION INSIDE
 OF AN ERRSET, THE NEXT TIME YOU DO A ↑ (WHICH IN TURN DOES (ERR NIL))
 CONTROL IS TRANSFERED TO A POINT ON THE STACK WHICH IS NO LONGER
 VALID. THIS CAN BE FIXED, AND PROBABLY WILL BE IN THE NEXT RELEASE.
 THE PROBLEM WITH THE LEVEL NUMBER IS NOT SO SIMPLE. GO AND OK
 ARE EXPECTING THE EXPRESSION TO RETURN A VALUE. AFTER THE VALUE
 IS RETURNED, THE LEVEL # IS DECREMENTED. SINCE GO AND RETURN
 SKIP OVER ALL OF THAT AND IMMEDIATELY RETURN TO THE LEVEL OF
 THE PROG, THE LEVEL # REMAINS UNCHANGED, AS DO THE IO CHANNELS AND
 THE PROMPT CHARACTER. YOU WILL GET A SIMILAR PROBLEM IF THE BROKEN
 EXPRESSION CONTAINS A RETFROM, EXCEPT THAT RETFROM HANDELS ERRSETS.
 I WILL GIVE A LOT OF THOUGHT TO THIS AND SEE WHAT I CAN COME UP WITH.
 IN THE MEANTIME DON'T USE GO OR OK ON GO OR RETURN. IF THE BREAK
 OCCURS BECAUSE OF AN ERROR, YOU CAN USE EX TO CONTINUE, BUT OTHERWISE,
 I AM AT LOSS AS TO WHAT TO SAY. SORRY.
 DARYLE
 -------

((EQUAL (CAR IN)(QUOTE QUOTE))(RETURN IN)) as second
clause in CHNMX in ERRORX.COM
T AND IMMEDIATELY RETURN TO THE LEVEL OF
 THE PROG, THE LEVEL # REMAINS UNCHANGED, AS DO THE IO CHANNELS AND
 THE PROMPT CHARACTER. YOU WILL GET A SIMILAR PROBLEM IF THE BROKEN
 EXPRESSION CONTAINS A RETFROM, EXCEPT THAT RETFROM HANDELS ERRSETS.
 I WILL GIVE A LOT OF THOUGHT TO THIS AND SEE WHAT I CAN COME UP WITH.
 IN THE MEANTIME DON'T USE GO OR OK ON GO OR RETURN. IF THE BREAK
 OCCURS BECAUSE OF AN ERROR, YOU CAN USE EX TO